1 of 4 special features ? 1024 bits or 16kb electrically programmable read only memory (eprom) communicates with the economy of one signal plus ground ? unique, factory-lasered and tested 64-bit registration number (8-bit family code, 36-bit serialization, 12-bit uniqueware identifier 5e7h, 8-bit crc-tester) assures absolute traceability because no two parts are alike ? built-in multidrop controller ensures compatibility with other 1-wire products ? eprom partitioned into 256-bit pages for randomly accessing packetized data records ? each memory page can be permanently write- protected to prevent tampering ? device is an ?add onl y? memory where additional data can be programmed into eprom without disturbing existing data ? reduces control, address, data, power and programming signals to a single pin ? directly connects to a single port pin of a microprocessor and communicates at up to 16.3 kbits per second ? presence detector acknowledges when reader first applies voltage ? low cost to-92 or 8-pin soic and 6-pin tsoc surface mount packages ? reads over a wide voltage range of 2.8v to 6.0v from -40c to +85c pin assignment pin assignment to-92 tsoc soic pin 1 ground ground nc pin 2 data data nc pin 3 nc nc data pin 4 ----- nc ground pins 5 to 8 ----- nc nc description uniqueware add-only memories are factory progr ammed versions of the ds2502 (1024 bit) and the ds2505 (16kb) add-only memories, respectively. they differ from the regular devices in their custom rom family codes (see ordering in formation) and the uniqueware identifier 5e7h in place of the upper 12 bits of the standard serialization field. for techni cal details on the devices pl ease refer to the ds2502 and ds2505 data sheets. uniqueware add-only memories are only available preprogrammed with customer-specific and write- protected data. uniqueware data fills at least one but no more than the first two pages of a device, depending on the length of the customer-supplied data. ds2502/5-unw uniqueware add-only memory www.maxim-ic.com 8 7 6 5 1 2 3 4 8-pin soic 1 2 3 6 54 top view 3.7 x 4.0 x 1.5 mm tsoc package to-92 gnd data nc bottom view 2 3 1 19-5069; 12/09 downloaded from: http:///
ds2502/5-unw 2 of 4 ordering information memory size family code package ordering part number 1024 bits 89h to-92 package ds2502u-pppp+ (4 pages) 8-pin 150 mil soic pkg. ds2502su-pppp+ 6-pin tsoc package ds2502pu-pppp+ 16kb 8bh to-92 package ds2505u-pppp+ (64 pages) 6-pin tsoc package ds2505pu-pppp+ pppp stands for the project id assigned to each indivi dual data pattern at the time of the first order. + denotes a lead(pb)-free/ro hs-compliant package. for tape and reel append t to the ordering part number. uniqueware devices are only available to existing cu stomers. new data patterns are no longer accepted. the minimum order quantity (moq) is 34,000 pieces with higher quantities available in multiples of 17,000 pieces in either bulk form or tape and reel. the tape and re el quantities are 2000 pieces (to-92), 4000 pieces (tsoc) and 2500 pieces (soic). the total order quantity (moq + additional 17,000 multiple) will cause a partial reel if the tape and reel device quantities are not an even multiple of the total order quantity. the shipment quantity can be plus or minus 10% of the order quantity. only the quantity shipped will be billed. sample uniqueware data structures sample 1: ethernet node address figure 1a (unused) crc16 company id value extension id value project id length msb lsb msb lsb msb lsb msb lsb 19 bytes 2 bytes 3 bytes constant 3 bytes serialization 4 bytes 1 byte ffh assigned by ieee constant 0ah high address low address physical address and data mapping figure 1b address 0c 0b 0a 09 08 07 06 05 04 03 02 01 00 data xx xx ch cm cl hh mm ll 00 00 pp pp 0a xx xx = inverted crc16, value depends on actual data ch cm cl = high, medium and low byte of the ieee assigned ?company id? hh mm ll = high, medium and low byte of the ?extension id? or serialization pp pp = project id assigned by maxim downloaded from: http:///
ds2502/5-unw 3 of 4 sample 2: eui-64 firewire tm node address figure 2a (unused) crc16 company id value extension id value project id length msb lsb msb lsb msb lsb msb lsb 17 bytes 2 bytes 3 bytes constant 5 bytes serialization 4 bytes 1 byte ffh assigned by ieee constant 0ch high address low address physical address and data mapping figure 2b address 0e 0d 0c 0b 0a 09 08 07 06 05 04 03 02 01 00 data xx xx ch cm cl hh hm mm ml ll 00 00 pp pp 0c xx xx = inverted crc16, value depends on actual data ch cm cl = high, medium and low byte of the ieee assigned ?company id? hh hm mm ml ll = high, medium and low byte of the ?extension id? or serialization pp pp = project id assigned by maxim the examples shown here use the de fault data structure. this format is also known as udp (universal data packet) and is commonly used in 1-wire apis. th erefore, if using one of those apis one can call a high level function to read and veri fy the inverted crc16. the udp is defined in application note 114, 1-wire file structure , and the apis can be found in the 1-wire software development kits . firewire tm is a trademark of apple computer, inc. downloaded from: http:///
ds2502/5-unw 4 of 4 revision history revision date description pages changed changed the ordering information to lead free. 2 removed the ds2506u. 1, 2 removed instructions on how to set up a uniqueware project (no new projects). 2 added moq, tape and reel size, and shipment quantity information. 2 emphasized that the 16-bit crc is inverted. 2, 3 included an explanation of ?default data structure.? 3 12/09 changed notation of hexadecimal numbers from h to h. 1, 2, 3 downloaded from: http:///
|
